What to Look For

If you are experiencing problems when running Microsoft� DirectX� applications, the DirectX Diagnostic Tool can help you find the source of the trouble. Here are some of the things you should be looking for:

• Incorrect versions of DirectX components. In the Notes section of the DirectX Files page, look for warnings about Beta and debug files. Beta files are early test versions and should not be installed with commercial applications. Debug versions, which are used in program development and likewise should not be installed with the final product, can cause applications to run significantly more slowly than they do under the retail versions of the components.
• Lack of hardware acceleration. Some programs run very slowly or not at all unless Microsoft DirectDraw® or Direct3D® hardware acceleration is available. On the Display page, look under DirectX Features to see whether DirectDraw, Direct3D, or AGP Texture acceleration is marked "Not Available." If so, you might consider upgrading your hardware.
• Device not connected. If a joystick or other input device fails to respond, it may not be properly set up. Make sure the device is accounted for on the Input page of the DirectX Diagnostic Tool. If not, add the device through Control Panel.
• Unsigned drivers. Microsoft has not tested Unsigned drivers for full compatibility with the latest version of DirectX. These drivers are listed on the appropriate component page.

Note: If you use Terminal Services to work on a remote system that supports hardware acceleration, the DirectX Diagnostic Tool might indicate support for hardware acceleration. However, Terminal Services can not use hardware acceleration, so support is not available.